Release 10.1A: OpenEdge Data Management:
SQL Development

Troubleshooting database connection problems

This section identifies common errors that occur while connecting to a database from a Java application using JDBC APIs, their possible causes, and solutions:

Error — [JDBC OpenEdge Driver]:Error in Network Daemon (8933)

Cause — A host-name of localhost was specified, either by default or through the –H option, when starting the OpenEdge database. This prevents connections from clients on other machines. Connections from only those clients that reside on the same machine as the database are allowed.

Solution — Shut down the database and restart it using the actual name of the host on which the database resides.

Error — error in tcp bind 10061

Cause — The port number or service name used in the URL to connect to the database is not the same as the one used to start the database.

Solution — Modify the port number or service name in your URL to match the one with which the database was started. This is designated by the –S option when starting the database.

Error — No suitable driver

Cause — The CLASSPATH is not specified correctly or is not set at all. The class name of the JDBC driver string, passed to the CLASS.FORNAME method, might be incorrect. The URL string might be incorrect.

Solution — Use the following guidelines for setting the CLASSPATH:

In Windows, ensure the CLASSPATH includes %DLC%\java\openedge.jar; %DLC%\java\util.jar; %DLC%\java\base.jar.
On UNIX, ensure the CLASSPATH includes $DLC/java/openedge.jar: $DLC/java/util.jar: $DLC/java/base.jar.
Check the JDBC driver string to see if it matches com.ddtek.jdbc.openedge.OpenEdgeDriver.
Check the URL string to see if it complies with the syntax of jdbc:datadirect:openedge://host_name:port;databaseName=database_name

or

jdbc:datadirect:openedge://host_name:port;databaseName=database_name;servicename=service_name